Skip to content

docs(readme): document .csproj usage and UNITY_MANAGED_PATH advanced config#34

Closed
NormandErwan wants to merge 1 commit into
claude/analyze-repo-issues-Ok1RZfrom
claude/update-readme-advanced-path-Yxwfv
Closed

docs(readme): document .csproj usage and UNITY_MANAGED_PATH advanced config#34
NormandErwan wants to merge 1 commit into
claude/analyze-repo-issues-Ok1RZfrom
claude/update-readme-advanced-path-Yxwfv

Conversation

@NormandErwan
Copy link
Copy Markdown
Owner

Summary

Follows on from #33 (the .csproj auto-detection rewrite) with the matching README updates:

  • Step 2 now includes DocFxForUnity.csproj in the list of files to copy, with a tip on renaming it and keeping docfx.json in sync.
  • Step 9 notes that Unity Hub DLLs are auto-detected — no manual "Open C# Project" step needed.
  • "Generate automatically" section also lists the .csproj in the diff block.
  • New "Advanced: custom Unity path (UNITY_MANAGED_PATH)" section explains the three-priority resolution order and shows the exact set/export commands for Windows, macOS, and Linux.
  • Removed the outdated troubleshooting tip that told users to open Unity and click Asset > Open C# Project to generate a .csproj.
  • Added a replacement troubleshooting entry pointing users to the new advanced section when DLLs are not found.

Test plan

  • Read through the rendered README on the PR page and verify formatting (tables, diff blocks, code blocks)
  • Confirm the UNITY_MANAGED_PATH paths match the globs used in DocFxForUnity.csproj
  • Confirm the removed "Open C# Project" tip is gone

https://claude.ai/code/session_01RvaYgaRCD7SfscrxeTynzu


Generated by Claude Code

@NormandErwan NormandErwan deleted the claude/update-readme-advanced-path-Yxwfv branch May 2, 2026 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant